Please use the customized Eclipse ME Plugin version that is distributed with the SMTK CD under the directory “EclipseMEplugin_WM” only for Eclipse 3.0.1 and 3.0.2 and install Eclipse ME as described in
Section 3.4. However, instead of selecting "eclipseme.feature_1. 2.3_site.zip" choose “\
EclipseMEpluging_WM\plugin.zip”
1 from SMTK CD after clicking the
New Archived Site… button.
To use the debugger it is necessary to increase the debug server delay timeout of Eclipse IDE. Please set the timeout under
Windows → Preferences → J2ME → Debug Server Delay to 25000. If you develop an extremely large application you may have to increase this timeout.
Eclipse ME Plugin 1.5.x is supported by the TC65, XT65/XT75 and AC65/AC75 CDs. This Eclipse ME Plugin is using a completely new device management concept to integrate different emulators. The integration and disintegration of the TC65 resp. XT65/XT75 or AC65/AC75 emulator is only automatically possible by using the TC65 resp. XT65/XT75 or AC65/AC75 SMTK CD!
Please note that selecting the TC65 resp. XT65/XT75 or AC65/AC75 emulator by using the Eclipse menu
Window → Preferences → J2ME → Device Management → Import and browsing to the respective emulator directory will not integrate the emulator.
Note: Manual emulator integration (by using Eclipse menu) is supported by Eclipse with using ME Plugin 1.5.5 and later. Automatic emulator integration using SMTK CD is possible for all Eclipse ME Plugin 1.5.x.
To use the debugger it is necessary to increase the debug server delay timeout of Eclipse IDE. Please set the timeout under
Windows → Preferences → J2ME → Debug Server Delay to 25000. If you develop an extremely large application you may have to increase this timeout.
You can easily switch between different installed emulators by using the properties of a project and choosing a Device Group, e.g. "Siemens IMP-NG XT75 Wireless Toolkit". You can select a device also by using the
Manage Devices… button, see figure below.
Automatic integration into Eclipse ME Plugin 1.6.x is supported by using the TC65 CD. All configurations, settings and using the Eclipse IDE are done in a very similar way as for Eclipse ME Plugin 1.5.x and are described in the
Section 11.3.2.5.1 and
Section 11.3.2.5.2.
To build the jar and jad files you have rebuild the project with the Create Package function. Open the context menu of the project and go to
J2ME → Create Package.
Note: Before starting Java debugging session with the HelloWorld-Sample it is recommended to check the setting of used emulator (e.g. TC65_R3 emulator in project properties see
Section 11.3.2.5.2), to clean the project with configuration "automatically build" (using Eclipse menu
Project → Clean…) and to compile it completely (using project’s context menu of the "HelloWorld" project select
J2ME → Create Package).
The integration of the SMTK using the SMTK installer depends selecting the offered default workspace “\workspace” of Eclipse (e.g. Eclipse 3.0.1 and 3.0.2 “..\eclipse\workspace\..” or Eclipse 3.1.0, 3.1.1 and 3.1.2 “..\Documents and Settings\<user name>\workspace\..”).
If you like to use the SMTK integration inside other workspaces, please integrate SMTK manually in these workspaces using Eclipse menu
Window → Preferences → J2ME → Platform Components (as shown in
Figure 36). Please keep in mind that all manually integrated SMTKs have to be removed manually as well in case of removing SMTK.
The Eclipse workspace directory differs from the location used under Windows 2000 and Windows XP. Using Windows Vista the following loaction is used for automatic integration of TC65 into Eclipse:
It is possible to start a debugging session without download of the Java files (*.jad and *.jar) again. The emulator has to be started with an additional parameter “-noload” and downloading of the Java files is suppressed. Please add the parameter in the following emulator configuration line as described in the figure:
Please keep in mind that you have to remove this emulator option before starting debugging session with download of Java files. The Java files are not updated in the Flash files system of the module while option “-noload” is set!
The option "-noload" does not take previously set breakpoints into account. In other words, if you have set breakpoints in your Java source file and would like to start the debugging session with the "-noload" parameter, no previous set breakpoint is reached.
During debugging it is sometimes possible, that if a breakpoint is reached, the Java program stops, but no breakpoint is indicated in the Java source line (Java source windows). In this case please select the Java Thread in the "Debug" window and select "System Thread" where the hit breakpoint is shown. The corresponding source line is highlighted inside the Java source windows (e.g. "HelloWorld.java") as well for the hit breakpoint. See the following figure.